@kujtimiihoxha I just ran the test suite locally and realised this has broken a test or two - will fix these up and ping you when the PR is actually ready for review, but will do this tomorrow!

@jesses-code-adventures What i have to actually change in this? or will you help me by this ?

@jesses-code-adventures might be that the tests that are failing are not related to your PR just so you know, I have not really done a good job maintaining the tests.

@ritikpal1122 I think you can close your old PR for now seems like this implements the necessary keymaps using the current config, thanks a lot for the effort you have put into this feature.

Ok nice one @kujtimiihoxha, I'll have a quick look today and see if it's anything my PR touches and let you know

Hey @kujtimiihoxha, the failing test is in internal/llm/tools/ls_test.go, as we panic if the config isn't loaded when calling config.WorkingDirectory(). This test also seems to be failing on main, so it appears to be unrelated to this PR.

t.Run("handles empty path parameter", func(t *testing.T) {
  // For this test, we need to mock the config.WorkingDirectory function
  // Since we can't easily do that, we'll just check that the response doesn't contain an error message
  
  tool := NewLsTool()
  params := LSParams{
	  Path: "",
  }
  
  paramsJSON, err := json.Marshal(params)
  require.NoError(t, err)
  
  call := ToolCall{
	  Name:  LSToolName,
	  Input: string(paramsJSON),
  }
  
  response, err := tool.Run(context.Background(), call)
  require.NoError(t, err)
  
  // The response should either contain a valid directory listing or an error
  // We'll just check that it's not empty
  assert.NotEmpty(t, response.Content)
})

Let me know your preference, happy to try get the test working, remove it, or just leave as-is. Cheers!

Maybe unrelated, but I also noticed when testing on a new machine that on both main and this branch, we throw an error if the user doesn't have a config file in $HOME/.opencode.json.

Would you like me to add the creation of a default config file if the user doesn't have one, or is this by design? Happy to add that in this PR or a separate one if desired.

Ok @kujtimiihoxha will revert or cancel my PR

but i want to contribute in more with @jesses-code-adventures Let ME know if i can join you

Maybe unrelated, but I also noticed when testing on a new machine that on both main and this branch, we throw an error if the user doesn't have a config file in $HOME/.opencode.json.

This is probably a bug, we should not require that.

@jesses-code-adventures I think for now just remove the failing tests, I will need to do real testing of everything soon.

no worries @kujtimiihoxha, have removed them now

@jesses-code-adventures looks like this needs a rebase, and there is a new global keymap ctrl+f for the file picker.

@kujtimiihoxha no worries, changes have been applied